|
In the fields of information technology and systems management, Application Performance Management (APM) is the monitoring and management of performance and availability of software applications. APM strives to detect and diagnose complex application performance problems to maintain an expected level of service. APM is "the translation of IT metrics into business meaning (() value)."〔(【引用サイトリンク】title=The Anatomy of APM )〕 == Measuring application performance == Two sets of performance metrics are closely monitored. The first set of performance metrics defines the performance experienced by end users of the application. One example of performance is average response times under peak load. The components of the set include load and response times. : * The load is the volume of transactions processed by the application, e.g., transactions per second (tps), requests per second, pages per second. Without being loaded by computer-based demands for searches, calculations, transmissions, etc., most applications are fast enough, which is why programmers may not catch performance problems during development. : * The response times are the times required for an application to respond to a user's actions at such a load. The second set of performance metrics measures the computational resources used by the application for the load, indicating whether there is adequate capacity to support the load, as well as possible locations of a performance bottleneck. Measurement of these quantities establishes an empirical performance baseline for the application. The baseline can then be used to detect changes in performance. Changes in performance can be correlated with external events and subsequently used to predict future changes in application performance.〔(【引用サイトリンク】title=APM and MoM -Symbiotic Solution Sets )〕 The use of APM is common for Web applications, which lends itself best to the more detailed monitoring techniques.〔(【引用サイトリンク】title=What You Should Know About APM – Part 1 )〕 In addition to measuring response time for a user, response times for components of a Web application can also be monitored to help pinpoint causes of delay. There also exist HTTP appliances that can decode transaction-specific response times at the Web server layer of the application. In their ''APM Conceptual Framework'', Gartner Research describes five dimensions of APM:〔(【引用サイトリンク】title=Keep the Five Functional Dimensions of APM Distinct )〕〔(【引用サイトリンク】title=Analytics vs. APM )〕〔(【引用サイトリンク】url=http://www.oracle.com/us/products/enterprise-manager/crimson-apm-comp-400465.pdf )〕〔(【引用サイトリンク】url=https://www.gartner.com/doc/2639025/magic-quadrant-application-performance-monitoring )〕 * End user experience monitoring - (Active and passive) * Application runtime architecture discovery and modeling * User-defined transaction profiling (also called business transaction management) * Application component monitoring * Reporting & Application data analytics 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Application performance management」の詳細全文を読む スポンサード リンク
|